Release 10.1A: OpenEdge Development:
Debugging and Troubleshooting

Event message formats

Event logging message formats correlate closely with event actions. There are six distinct formats.

Format 1: event occurs

Messages logged when an event occurs contain the following information:

Start — START.
Identifier — Event type GUI (GUI Windows), UI (character mode), PRGS, COM, ASYNC, or SOCKET.
Event name — For example, LEAVE or GUI WM_command. For WM_CHAR, also contains the key pressed.
Widget information — Type (BUTTON, for example), name, and handle ID of the object, when available.
Flag — T or F (COM events only). For use by Progress Software Corporation Technical Support.
OpenEdge Handled — The string Progress Handled appears only for COM object WM_ events.

Here are some sample Format 1 log entries:

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS START PRGS LEAVE BUTTON Handle:1989

[05/10/31@12:02:43.570-0400] P-005783 T-005735 2 4GL PROEVENTS START COM WM_KEYDOWN Handle:1114

[05/10/31@12:02:43.585-0400] P-005783 T-005735 2 4GL PROEVENTS START COM CtrlFrame.CSSpin.KeyDown CONTROL-FRAME Handle:1114 myocx.w T

[05/10/31@12:03:57.710-0400] P-005783 T-005735 3 4GL PROEVENTS START GUI WM_DESTROY FILL-IN customer-name Handle:1126

[05/10/31@12:02:43.570-0400] P-005783 T-005735 2 4GL PROEVENTS START COM WM_CHAR d Handle:1114

[05/10/31@12:02:43.570-0400] P-005783 T-005735 2 4GL PROEVENTS START COM WM_CHAR TAB Handle:1114

Format 2: indirect action

Messages logged when there is an indirect action contain the following information:

Identifier — Action.
Description — A textual description of the indirect action taken.

Here are some sample Format 2 log entries:

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS Action minimize related windows

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS Action close related windows

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS Action restore related windows

Format 3: pushed on to the stack/popped off the stack

Messages logged when an event is either pushed onto or popped off of the stack contain the following information:

Identifier — Push or Pop.
Event name — For example, LEAVE. For a keystroke, the entry includes the key name and associated event, if appropriate.
Widget information — Type (BUTTON, for example), name, and handle ID of the object, when available.
Procedure name — Name of the procedure that created the object (not available in all cases).

Here are some sample Format 3 log entries:

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS PUSH ENTRY BUTTON button-1 Handle:1564 myproc.p

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS PUSH ENTRY BUTTON Handle:1987

[05/10/31@12:19:54.023-0400] P-005805 T-005881 2 4GL PROEVENTS PUSH CTRL-F FILL-IN X Handle:1000 test.p

[05/10/31@12:20:45.054-0400] P-005805 T-005881 2 4GL PROEVENTS PUSH F6 (NEXT-FRAME) FILL-IN X test.p

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS POP ENTRY BUTTON Handle:1987

Format 4: generated by the 4GL APPLY statement

Messages logged when an APPLY statement executes contain the following information:

Identifier — APPLY.
Event name — For example, LEAVE. For a keystroke, the entry includes the key name and associated event, if appropriate.
Widget information — Type (BUTTON, for example), name, and handle ID of the object, when available.
Routine name and line number — Name and line number of the routine (.p or .w file or method) and internal procedure, if appropriate, where the APPLY statement is. The line number is based on the Debugger listing file.

Here are some sample Format 4 log entries:

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS APPLY ENTRY BUTTON button-1 myproc myp.p Line 10

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS APPLY ENTRY BUTTON Handle:1987 myproc myp.p Line 10

Format 5: trigger execution

Messages logged when a trigger executes contain the following information:

Identifier — Begin-Trigger or End-Trigger.
Additional information — Can include: the event name, for example, LEAVE; object type and name, and handle ID (when available), or internal procedure name for persistent triggers; the word ANYWHERE, if it is an ANYWHERE trigger. For objects that are no longer valid, the entry also includes the words object not valid, as in the case when the window following it has been destroyed.
Procedure name — Name of the routine (.p or .w file or method) and internal procedure, if appropriate, where the trigger is.

Here are some sample Format 5 log entries:

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS Begin-Trigger "LEAVE OF button button-1" Handle:1234 myprog.p

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS End-Trigger "LEAVE OF button button-1" Handle:1245

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS Begin-Trigger "LEAVE OF button" RUN myinternalproc Handle:1256 myproc.p

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS Begin-Trigger "F2 OF FILL-IN" ANYWHERE Handle:1278 myproc.p

Format 6: event discarded

Messages logged when an event is discarded contain the following information:

Identifier — PRGS.
Event name — For example, ENTRY.
Additional information — In most cases, the word discarded, followed by the reason for not processing the event, if known; for example, widget disabled.
Widget information — Type (BUTTON, for example), name, and handle ID of the object, when available.

Here are some sample Format 6 log entries:

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS PRGS ENTRY BUTTON b1 Handle:1234 discarded widget disabled

[05/10/31@13:00:00.098-0400] P-000001 T-000002 2 4GL PROEVENTS PRGS ENTRY BUTTON Handle:1987 discarded widget disabled

[05/10/31@12:36:32.226-0400] P-005747 T-005914 2 4GL PROEVENTS PRGS ESC (END-ERROR) FILL-IN FILL-IN-1 Handle:1568 discarded

[05/10/31@12:37:32.226-0400] P-005747 T-005914 2 4GL PROEVENTS PRGS LEAVE FILL-IN FILL-IN-1 Handle:1598 discarded return no-apply

[05/10/31@12:38:32.226-0400] P-005747 T-005914 2 4GL PROEVENTS PRGS ESC FILL-IN FILL-IN-1 (END-ERROR) Handle:1599 field validation failed